Notification of the availability of electronic bills

ABSTRACT

To notify a person of the availability of electronic billing information, billing information associated with bills of a biller for its customers is stored in a first data store, and identify information identifying unregistered persons having billing information stored in the first data store, is stored in a second data store. Registration information identifying a person who is currently unregistered is received via a wide area network. The received registration information is compared with the identity information stored in the second data store. Based on the comparison, it is determined if the received registration information identifies a customer of the biller. If so, a notice of the availability of the stored billing information of the biller is transmitted to the person via the wide area network.

RELATED APPLICATIONS

This application is a divisional of application Ser. No. 09/734,694,filed Dec. 13, 2000, and entitled “DYNAMIC BILLER LIST GENERATION”,which is a continuation-in-part of application Ser. No. 09/298,889,filed Apr. 26, 1999, and entitled “ELECTRONIC BILL PRESENTMENT AND/ORPAYMENT CLEARING HOUSE”, the contents of which are incorporated byreference herein in their entirety.

TECHNICAL FIELD

The present invention relates generally to electronic bill presentmentand/or payment. More specifically, the present invention relates tonotifying users of the availability of electronic bill information.

BACKGROUND ART

Over the past several years an international network of networks knownas the Internet has become increasingly popular. The Internet allowsmillions of users throughout the world to communicate with each other.To provide users with easier access to information available onInternet, a World Wide Web has been established. The World Wide Weballows information to be organized, searched and presented on theInternet using hypertext. Thus, using the World Wide Web a user cansubmit a query for information and be linked electronically toinformation of interest which has been stored at web locations on theInternet. Using hypertext, a user can also communicate information toother users of the Internet. Hence, the Web has made it relatively easyfor virtually anyone having access to a personal computer or otherdevice connected to the Internet to communicate with others who are alsoconnected to the network.

With the proliferation of Internet users, numerous services are nowprovided over the Internet. One of the first such services to be offeredwas electronic banking. Electronic banking allows banking customers toaccess their account information and execute banking transactions, e.g.the transfer of funds from a savings to checking account, by simplylinking to a bank server using the Internet to access accountinformation and communicate transfer instructions.

More recently, it has become possible to electronically pay bills bycommunicating instructions, via the Internet, to a financial institutemaintaining deposited or credited funds of a pre-registered payer, or toa representative of the financial institute. The payments are then madeto the payee by the financial institute or its representative. Fundsfrom the payer's deposit or credit account, i.e. the payer's account,are debited by the financial institute to cover the payment. The paymentby the financial institute or its representative to the payee can bemade in any number of ways.

For example, the financial institute or representative mayelectronically transfer funds from the payer's account to the payee'saccount, may electronically transfer funds from a financialinstitute/representative's deposit or credit account, to the payee'saccount, may prepare a paper draft on the financialinstitute/representative account and mail it to the payee, may preparean electronically printed paper check on the payer's account and mail itto the payee, or may make a wire transfer from either the financialinstitute/representative account or payer's account.

If the funds transferred to the payee are drawn from the financialinstitute/representative account, funds from the payer's account areelectronically or otherwise transferred by the financial institute tothe financial institute/representative account to cover the payment.Further, if the payment will be made from funds in the financialinstitute/representative account, the payment will preferably beconsolidated with payments being made to the same payee on behalf ofother payers.

Accordingly, such electronic bill payment systems eliminate the need fora payer to write or print paper checks and then forward them by mail tothe payee. This makes it easier and more efficient for the payer to makepayments. Payees receiving consolidated payments no longer have to dealwith checks from each payee and therefore can process payments moreefficiently. The making of payments by the electronic or wire transferof funds provides even further efficiencies in payment processing bypayees, and it is well recognized that making payments electronicallycan significantly reduce the cost of processing payments for both thepayer and payee.

The number of users of electronic bill payment services has growndramatically since introduction by CheckFree Corporation, the assigneeof the present application. However, because the billing side of thebilling/payment process had not been integrated with the electronicpayment process, many potential users remained reluctant to utilize theservice.

More particularly, until the offering by CheckFree Corporation,electronic bill payment systems were operated independent of the billpresentment process. Still today, most conventional electronic billpayment systems generally require that the payee receive a conventionalpaper bill from a merchant or other billing entity, the exception beingfor certain bill payments, such as mortgage payments, which can bepre-authorized by the payee. Thus, for most bill payments, it is onlyafter the paper bill has been received that the payee can connect to theelectronic bill payment system via the Internet and provide a paymentinstruction.

Using CheckFree's fully integrated electronic bill presentment andpayment system, registered merchants and other payers can electronicallypresent bills to registered consumers and other payees by communicatingbills via the Internet, to the electronic presentment/payment serviceprovider, which could be a financial institute/representative or someother service provider. Typically, the bill is stored centrally on theelectronic presentment/payment system server. The service providernotifies the payer, for example by Internet email, of the availabilityof the bill and the bill can then be accessed by the payer by connectingto the system server or some other server, via the Internet, to retrievethe bill. Once connected to the system server, the payer can alsocommunicate a payment instruction to the server and the payment can thenbe made to the payee as previously described.

Accordingly, CheckFree's electronic bill presentment and payment systemeliminates the need for a payee to print paper bills and then forwardthem by mail to the payer. This makes it easier and more efficient forthe payee to issue bills. Payers receiving electronic bills no longerhave to deal with paper bills from each payer. The combination ofelectronic presentment and payment of bills has provided even furtherefficiencies and cost reductions in billing and payment processing byboth payers and payees.

Although electronic bill presentment and particularly integratedelectronic bill presentment and payment have received broad useracceptance from both payers and payees, there remains a significantnumber of payers using electronic bill presentiment and payment serviceswho are not taking full advantage of the benefits of the electronic billpresentment facet of the services. These payers may not electronicallyreceive all of their bills which are available in the electronicpresentment form. Instead, these payers continue to receive some billsin paper form and make payments in either electronic or paper form.Oftentimes this is because the electronic payers are unaware that aparticular payee offers electronic presentment.

One reason a payer may be unaware of the availability of electronicbills from a particular payee is that the community of payees who offerelectronic bill presentment is ever-growing. Thesenew-to-electronic-bill-presentment payees often have not informed theircustomers in a timely manner that electronic bill presentment isavailable. There is also a segment of the users of integrated electronicbill payment and presentment services who are unaware that any of theirpayees offer electronic bill presentment. Accordingly, a need exists fora technique to inform bill presentment and payment service users thatelectronic bill presentment is available, whether these customers arealready taking advantage of electronic bill presentment to some extent,or whether they simply use the payment side of the service, to increaseusage of electronic bill presentment.

As described above, electronic bill presentment offers significantbenefits to payees. However, to gain these benefits, a payee who offerselectronic bill presentment must be able to identify those payers whomight wish to utilize electronic bill presentment. Currently, the onlyway for payees to identify a payer for electronic bill presentment is toreceive a request for electronic bill presentment from that payer. Thepayee might also identify a payer for electronic bill presentment basedon knowledge that a payer currently makes payments electronically tothat payee. By being able to identify consumers who utilize electronicbill presentment and payment services for purposes unrelated toreceiving or paying a payee's bill, a payee could efficiently focus itsefforts to recruit new payers into the payee's electronic billpresentment and payment community of users. Accordingly, a need existsfor a technique which will allow electronic billers to identify payerswho may be amenable to electronic bill presentment and/or payment, toincrease usage of electronic bill presentment and/or payment.

OBJECTIVES OF THE INVENTION

It is accordingly an objective of the present invention to provide atechnique which will facilitate increased usage of electronic billpresentment.

Additional objects, advantages, novel features of the present inventionwill become apparent to those skilled in the art from this disclosure,including the following detailed description, as well as by practice ofthe invention. While the invention is described below with reference topreferred embodiment(s), it should be understood that the invention isnot limited thereto. Those of ordinary skill in the art having access tothe teachings herein will recognize additional implementations,modifications, and embodiments, as well as other fields of use, whichare within the scope of the invention as disclosed and claimed hereinand with respect to which the invention could be of significant utility.

SUMMARY DISCLOSURE OF THE INVENTION

The present invention provides a system and method for processing billpayment information. The system includes at least one processor, amemory for storing data, and a communications port for transmitting andreceiving information, including bill payment information. The processormay be any type processor, such as a personal computer, high poweredworkstation, or sophisticated main-frame processor. The memory also maybe type memory capable of storing data, including random access memory,floppy or hard magnetic disk, or optical disk. Data stored in the memoryand data processed by the processor are exchanged between the processorand the memory. The data can include bill payment information andoperating instructions for controlling the operations of the processor.The communications port may be connected to a network configured totransmit electronic or optical data. The network can include a public orprivate telephone network, the Internet, or any other type network. Billpayment information can include directions to pay a bill, informationidentifying payers, payees, billers, customers, financial institutions,and/or data representing accounts maintained at financial institutions.The bill payment information could also, or alternatively, includeinformation identifying parties to financial transactions that may ormay not take place in the future.

In accordance with the invention, the processor processes informationidentifying a payee to whom a payer intends to electronically directpayment. This identifying information may be information stored in thememory, it may be information received via the communications port, orit may be information received by the processor in some other manner.The information may be information received from the payer and processedprior to storage in the memory, or it may be processed subsequent tostorage in the memory. The information could, if desired, be received,processed in a manner unrelated to bill payment, stored, and thenretrieved and processed again. The information identifying the payeecould be, but preferably is not, associated with a directive to make apayment to that payee.

The processor processes the information to determine if bills of thepayee are available electronically. That is, are bills issued by thepayee, also sometimes referred to as a biller, available in electronicformat as opposed to a traditional format in which bills are presentedon paper to a payee, also sometimes referred to as a customer.

If the processor determines that bills issued by the identified payeeare available, electronically, i.e. are either already available inelectronic form or could be made available in electronic form, theprocessor directs that a notice be transmitted to the payer notifyingthe payer that the bills of the payee are available electronically. Thisnotice may be transmitted via any network of computers, any telephonenetwork, or even via traditional mail.

Beneficially, the processor directs that information identifying thepayee be transmitted to the payer along with notice that bills from thispayee are available electronically.

Advantageously, the system also can include several different databasesstored in the memory. For example, a database for storing informationidentifying a payee to whom a payer intends to electronically makepayment may be stored. This database is referred to as a payeepick-list. The payee pick-list database can include informationidentifying more than one payee. As discussed above, the informationidentifying the payee may be processed either after storage, whichcould, in this case be storage in the payee pick-list database, or priorto storage in the payee pick-list database.

Preferably, the memory stores a plurality of payee pick-lists. Each ofthe payee pick-lists is associated with a different payer. Each payeepick-list can also include information indicating which of the includedpayees offers electronic bill presentment, as well as the availabilityof electronic bill information.

In accordance with a particularly preferred aspect of the invention, theinformation identifying the payee may be processed by the processor morethan once. If initial processing determines that the bills of the payeeare not available electronically, the processor will subsequentlyprocess the information again. If this subsequent processing determinesthat the bills of the payee are available electronically, the payer isthen informed as discussed above. This subsequent processing may beperformed periodically or based on a triggering event so thatinformation regarding availability is updated routinely.

Another of the databases which may be stored in the memory is a databasestoring information identifying payees that offer electronic billpresentment. The processor can be configured to access this database todetermine if a payee is included in this database.

Yet another of the databases which may be stored in the memory is adatabase storing information identifying payees that have presented oneor more electronic bills. This database is sometimes referred to as abiller database. The processor can be configured to access this databaseand determine if a payee is included in this database.

Still another of the databases which may be stored in the memory is adatabase storing electronic billing information. The electronic billinginformation may relate to payers who have paid a bill electronically,payers who have received a bill electronically, payees who havepresented a bill electronically, payees who presently present billselectronically, stored electronic bills, and may include otherinformation associated with a bill. The processor can be configured toaccess this database and determine if information associated with apayee is included in this database. Preferably, the processor is alsoconfigured to access this database and determine if a stored electronicbill for a payer and associated with the payee is stored in thedatabase. If so, the processor directs a further notice be transmittedto the payer notifying the payer that the stored electronic bill isavailable.

In another beneficial aspect of the invention, a processor, such as auser computer, can be configured to receive, responsive to thetransmitted notice, an inputted request from the payer to receive thebills of the payee electronically. If desired, the processor can,responsive to receipt of the inputted request, cause the request to betransmitted to the payee via, for example, a hyper-link, batch transferor other communication.

Still another of the databases which may be stored in the memory is adatabase storing information identifying payers having stored electronicbills in the database storing electronic billing information. Thisdatabase is sometimes referred to as a customer database. The processormay be configured to access this database to determine if a payer isincluded in this database before accessing the database storingelectronic billing information to determine if a stored electronic billfor the payer and associated with a payee is stored in that database. Ifthe payer is not included in the customer database, the processor neednot access the database storing electronic billing information.

Preferably, the processor is also configured to receive an electronicbill, which could be in the form of full or summary bill information inany format, from a payee directed to a payer. The processor processesthis electronic bill to determine if the payee is included in thedatabase storing information identifying those payees having presentedat least one electronic bill, discussed above and referred to as thebiller database. If not, information identifying the payee is added tothis database.

If information identifying the payee is not included in the billerdatabase, then an indication that the payee offers electronic billpresentment will not be stored in any payee pick-list. Beneficially, tokeep each pick-list current, if the payee is not included in the billerdatabase the processor can be configured to identify the payeepick-lists in which the payee is identified and store informationidentifying the payee as a payee offering electronic bill presentment ineach of the identified payee pick-lists.

Another of the databases that can be stored in the memory is sometimesreferred to as a master payee pick-list. The master payee pick-listincludes information identifying every payee included in each of theindividual payee pick-lists for each payer. The master payee pick-listmay also include information identifying each payer having identified apayee in an individual payee pick-list. In which case, each payee isassociated with each respective identified payer.

The processor is optionally configured to access the master payeepick-list and to determine, if the payee is not included in the billerdatabase, if that payee is included in the master payee pick-list. Ifso, the processor determines which of the payers are associated with thepayee. The processor then stores information identifying the payee as apayee that offers electronic bill presentment in each individual payeepick-list associated with an identified payer.

The processor may additionally be configured to store a receivedelectronic bill. Beneficially, the processor can also be configured totransmit a notice to a payer that the electronic bill is available. Aswith the above-discussed notice, the transmission may take on any ofseveral forms.

In accordance with another particularly preferable aspect of theinvention, the processor is configured to determine if a payer isassociated with an individual payee pick-list. If so, the processor candetermine if a payee is included in that payer's individual payee-picklist. And, if so, the processor stores an indication of availableelectronic billing information from the payee in that payer's individualpayee pick-list. This processing ensures that the payee's individualpayee pick-list is kept current as to availability of any storedelectronic billing information.

To keep the customer database current, the processor may be configuredto access the customer database and determine if a payer is included. Ifnot, information identifying the payer can be stored in the customerdatabase.

The processor may also be configured to determine if a payee is includedin the master payee pick-list, even if the payee is included in thebiller database. If a payee is included in the master payee pick-list,the processor can determine if a payer is associated with that payee inthe master payee pick-list. If so, the processor stores an indication ofavailable electronic billing information from that payee in that payer'sindividual payee pick-list.

In another embodiment of the invention, computer programming is storedon a computer readable medium. The computer readable medium is readableby a computer to cause the computer to operate as discussed above. Thatis, the programming stored on the computer readable medium causes acomputer to perform each desired aspect of the invention discussedabove.

In another aspect of the invention, information is received whichidentifies a person, a deposit account associated with the person, and afinancial institution at which the deposit account is maintained.Information identifying the person need never have been received before.Electronic billing information is stored in a first database. Otherinformation identifying unregistered persons having electronic billinginformation stored in the first database is stored in a second database.A determination is made as to whether the other information stored inthe second database identifies the person. If so, the person is notifiedof the availability of stored electronic billing information whichidentifies the person. Thus, a person who is unregistered can benotified of stored billing information immediately upon becomingregistered.

In yet another aspect of the invention, a method for notifying a payerof the availability of electronic bill presentment is disclosed. Aninstruction to pay a bill of a payee is received via a network. Adatabase is accessed which contains information identifying payees whooffer electronic bill presentment. A determination is made as to whetherthe payee is included in the database. If so, the payer is notified thatthe payee offers electronic bill presentment.

Advantageously, a request to receive electronic bills from the payee isreceived from the payer. The payee is notified that the payer requeststo receive the electronic bills. The notification to the payer may bevia a hyper-link, batch transfer or other communication. Beneficially,electronic bill presentment options may be transmitted to the payer. Arequest from the payer is input to select one of the options. Thisinputted request is transmitted to the payee.

Another database may be accessed which stores information identifyingstored electronic billing information. If it is determined thatelectronic billing information for the payer is stored in this otherdatabase, the payee is notified of the availability of the storedelectronic billing information. A request from the payer to access thestored information may be entered by the payer. A hyper-link can beactivated responsive to receipt of the request and the storedinformation may be transmitted to the payer via the hyper-link.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 depicts an electronic bill presentation and payment network inaccordance with the present invention.

FIG. 2 depicts the communications between various network stationsdepicted in FIG. 1, in accordance with the present invention.

FIG. 3 is a flow chart showing the operations which are performed by thenetwork stations of FIG. 2, in accordance with the present invention.

FIG. 4 depicts the communications between various network stationsdepicted in FIG. 1 to direct payers to electronic bills, in accordancewith the present invention.

FIG. 5 is a flow chart showing the operations which are performed by thenetwork stations in FIG. 4, in accordance with the present invention.

FIG. 6 depicts the communications between various network stationsdepicted in FIG. 1 to pay paper bills, in accordance with the presentinvention.

FIG. 7 is a flow chart showing the operations which are performed by thenetwork stations in FIG. 6, in accordance with the present invention.

FIG. 8 is a simplified depiction of a central database for storingelectronic billing and remittance information, in accordance with thepresent invention.

FIG. 9 is a simplified depiction of a registered user/biller databasefor storing a list of registered users who are electronic billers, inaccordance with the present invention.

FIG. 10 is a flow chart showing the operations which are performed bythe central clearinghouse station processor to maintain a registereduser/biller database.

FIG. 11 is a simplified depiction of a registered user/customer databasefor storing a list of registered users who are customers, in accordancewith the present invention.

FIG. 12 is a flow chart showing the operations which are performed bythe central clearinghouse station processor to maintain a registereduser/customer database.

FIG. 13 is a simplified depiction of an unregistered user/customerdatabase for storing a list of unregistered users who are customers, inaccordance with the present invention.

FIG. 14 is a flow chart showing the operations which are performed bythe central clearinghouse station processor to maintain a unregistereduser/customer database.

FIG. 15 is a simplified depiction of an individual payee pick-list forstoring information identifying payees a user may plan to payelectronically.

FIG. 16 depicts the communications between various network stationsdepicted in FIG. 1 to maintain an individual user's payee pick-list.

FIG. 17 is a flow chart showing the operations which are performed bythe network stations in FIG. 16, to maintain an individual user's payeepick-list in accordance with the present invention.

FIG. 18 is a flow chart showing the operations which are performed bythe network stations of FIG. 16 to utilize an individual user's payeepick-list.

FIG. 19 is a simplified depiction of an individual payee pick-list aspresented to a user via a network connection to select a payee forpayment.

FIG. 20 is a simplified depiction of a payment screen as presented to auser via a network connection to make a payment.

FIG. 21 is a simplified depiction of a sign-up screen as presented to auser via a network connection to sign-up for electronic billpresentment.

FIG. 22 is a flow chart showing the operations which are performed bythe network stations of FIG. 16 to indicate electronic bill presentmentavailability.

FIG. 23 is a flow chart showing the operations which are performed bythe network stations of FIG. 16 to indicate stored billing informationavailability.

FIG. 24 is a flow chart showing alternative operations which areperformed by the network stations of FIG. 16 to indicate bothavailability of electronic bill presentment and availability of storedbilling information.

FIG. 25 presents alternative communications between various networkstations depicted in FIG. 1 to maintain an individual user's payeepick-list, a master payee pick-list, and to include additionalinformation in an individual payee pick-list.

FIG. 26 is a flow chart showing alternative operations which areperformed by the network stations of FIG. 25 to maintain individualpayee pick-lists and to indicate availability of additional information.

FIG. 27 is a simplified depiction of a master payee pick-list forstoring information identifying every payee identified by at least oneuser for inclusion in an individual user's payee pick-list.

FIG. 28 is a flow chart showing operations performed by the networkstations of FIG. 25 to maintain a master payee pick-list.

FIG. 29 is a flow chart showing alternative operations performed by thenetwork stations of FIG. 25 to determine if a new registered user/billeris included in a payee pick-list.

FIG. 30 is a flow chart showing operations performed by the networkstations of FIG. 25 to determine if a new registered user/customer hasincluded the biller in its payee pick-list.

FIG. 31 is a flow chart showing alternative operations performed by thenetwork stations of FIG. 25 to determine if a new registereduser/customer has included the biller in its payee pick-list.

FIG. 32 is a flow chart showing operations performed by the networkstations of FIG. 1 to register a previously unregistered user.

BEST MODE FOR CARRYING OUT THE INVENTION

As shown in FIG. 1, a bill presentment and payment network 100 includesa large number of user stations represented as payee and payer userstations 110A-110H, respectively representing payees and payers A-H. Itwill be recognized that the network 100 preferably includes manythousands if not millions of user stations. The user stations arecapable of communicating via the Internet 150, although it will beunderstood that some other communications network could be utilized inlieu of the Internet.

Also included in the network 100 are a large number of financialinstitute (FI) user stations 130A-130D, respectively representingfinancial institutes I-L. The FI stations 130A-130D are capable ofconnecting to a communications network 160 which could be the Internetand/or a more secure communications network such as the conventional ACHcommunications network or some other inter-bank communications network.Additionally included in the network 100 is a central clearinghousestation 140. Station 140 includes a processor 140A and memory 140B. Thememory 140B stores databases 140B3-140B5 for storing user-classinformation, as will be discussed below, databases 140B6 and 140B7 forstoring payee information, as will be discussed below, and programmedinstructions 140B1. The memory 140B also stores a relational database140B2 for storing billing and remittance information. Each user A-H hasa deposit and/or payment account, each to be called an account herein,maintained at one of the financial institutes I-L.

Although, as shown, each of the user stations 110A-110H can communicatewith the central clearinghouse station 140 via the Internet 150, forpurposes of the following description, only certain of users A-H areregistered to electronically present and/or pay bills on network 150,see FIGS. 8, 9, 11 and 13. More particularly, for purposes of thefollowing discussion, users D, F and G are unregistered users of network0.100. Further, user A is an individual and users B and H are smallbusiness entities. User E is a large business entity.

To facilitate the use of the electronic bill presentment and paymentservices, the central clearinghouse station 140 operates in accordancewith instructions 140B1, to perform a registration process. For someusers, the registration process may require only that the user provideits identification, its account number and an identification of afinancial institute at which its account is maintained. In any event,this information is stored in the relational database 140B2 inassociation with a user identifier and an identifier indicating that theuser is a registered user. Having this information, the centralclearinghouse station processor 140A can now direct payments, preferablyby electronic fund transfer, to the account of a registered user. Thecentral clearinghouse station processor 140A can also now directspayments, preferably by electronic fund transfer, from the account of aregistered user to make a payment directed by that registered user. Thecentral clearinghouse station processor 140A also operates to generateremittance information for each payment directed to a user, registeredor unregistered, as will be further described below, and to direct thestorage of such information in the relational databases 140B2 inassociation with the user identifier. Thus, the database 140B2 serves asa temporary depository for remittance information corresponding to anypayment directed to a user on behalf of registered network users.

To central clearinghouse station 140, individuals, small businesses, andlarge businesses appear the same. The central processor 140A alsofunctions to generate user-class information for each bill received froma registered user for electronic presentment, as will be discussedbelow.

The central processor 140A also operates to generate billing informationfor each bill, whether including full or summary information, receivedfrom a registered user for payment by another user and to direct thestorage of such information in the relational database 140B2 inassociation with the other user's identifier. Thus, the relationaldatabase 140B2 serves as a temporary depository for billing informationwhich may be provided by any of the registered users. Registered userswho provide electronic bills for payment by other users are also knownas billers. Users to whom received electronic bills are directed arealso known as customers.

The central processor 140A preferably further functions toelectronically receive bills from registered billers in the form outputby any commonly used standard invoicing software packages, such asQuickbooks, Peachtree and other off-the-shelf invoicing software, oralternatively in ASCII or other formats and, if necessary, to convertthe received bill into standard format billing information for storagein the database 140B2 in relationship with the applicable customeridentifier for subsequent presentment to the applicable user station110A-H. Accordingly, registered billers need not modify their existinginvoicing software or substantially modify their existing procedures,other than to transmit the bill output from their existing invoicingsoftware via the Internet 150 to the central clearinghouse station 140,to have their bills electronically presented to the applicable customer.

The central clearinghouse station processor 140A is also preferablycapable of generating remittance information in multiple standardformats, compatible with all the commonly used accounts receivable orinvoicing software, and in ASCII or other formats. The central processor140A directs the storage of the formatted remittance information in thedatabase 140B2 of memory 140B in association with the applicable useridentifier. The remittance information can be generated and stored inall the above mentioned formats. Alternatively, the applicable billercan select, or otherwise identify, a particular one of the formats inwhich it wishes to receive remittance information. Using this lateralternative, the remittance information is formatted and stored only inthe requested format. Accordingly, registered billers can obtainremittance advice by simply using a browser to contact the centralclearinghouse station 140 and requesting the stored remittanceinformation. Responsive to the request, the central clearinghousestation processor 140A retrieves the applicable remittance informationfrom the database 140B2 and transmits the information via the Internet150 to the applicable user station. Because the information willtypically be received in at least one format usable by the biller'sstandard invoicing software, this information can be directly input tothe accounts receivable system and processed in the conventional manner.

FIG. 2 depicts the communications between various network stations toelectronically present and pay bills. Turning to FIGS. 2 and 3, user Aand user H are registered in step 300 of FIG. 3. User H, who is also abiller and represented by user station 110H, generates, in step 310 inFIG. 3, a bill to user A, represented by station 110A. The bill may begenerated by a standard software package or otherwise. The output of thesoftware, which represents the bill, is transmitted in communication 205from the user station 110H to the central clearinghouse station 140, asindicated in step 315 of FIG. 3. The central clearinghouse stationprocessor 140A, in accordance with programmed instructions 140B1,processes the received bill to generate standard format billinginformation in step 320.

The central processor 140A also determines if user A is a registereduser, as indicated in step 321. If so, as is the case here, the centralprocessor 140A, in communication 210A, directs the storage of thebilling information in the relational database 140B2 of the memory 140Bin association with the user A identifier, as shown in step 325.

Additionally, central processor 140A may optionally generate andtransmit a notification to user station 110H notifying user station 110Hof the registration status of user A, as indicated by communication 280and step 328. Biller H may then inform the customer, perhaps incorrespondence enclosed with a paper copy of the bill mailed to user A,that billing and/or payment is available electronically, therebymotivating the registered user to utilize electronic bill payment and/orpresentment.

The central processor 140A may also optionally generate and transmit anotification to the user station 110A of the availability of storedbilling information, as indicated by communication 215 and step 330, ifthe user to whom the bill is directed is a registered user.

If the bill were for unregistered user D rather than registered user A,central processor 140A determines if a user D identifier is stored indatabase 140B2 at step 322. If unregistered user D has previously beenpaid by a registered user, or if a registered user has submitted anelectronic bill for payment by user D, an identifier for user D willalready be stored in database 140B2. If so, operations continue withstep 325. If not, a user D identifier is generated based upon thebilling information and stored in database 140B2, as indicated bycommunication 285 and step 323. Next, the generated billing informationis stored in the database 140B2 in association with the user identifier,as indicated by communication 210B and step 325. Thus, after completionof step 323, operation continue as described above and depictedbeginning at step 325.

A request for the billing information, as indicated in step 335, isreceived via communication 220 at the central clearinghouse station 140from station 110A. The central processor 140A determines whether or notthe request is from a registered user in step 337. If the request werefrom unregistered user D rather than registered user A, the centralprocessor 140A would transmit a query to station 110D to determine ifuser D desires to register and thereby obtain access to its billinginformation which is stored on database 140B2. Optionally, anunregistered customer could be provided with limited access to itsstored electronic billing information to sample electronic billpresentment based upon providing sufficient information to verify thecustomer's identity, but without the need to provide an account numberand associated financial institute information.

Thus, it should be understood that the central clearinghouse station 140operates to generate and direct the storage of billing information inassociation with registered and unregistered user identifiers, as may bedesired by a registered user. If billing information for an unregistereduser is stored in database 140B2, the biller may inform the unregisteredcustomer, perhaps in correspondence enclosed with a paper copy of thebill mailed to the unregistered user, that the bill is available andpayable electronically and can be accessed by contacting the centralclearinghouse station 140 at its Internet web site, thereby motivatingthe unregistered user to register for electronic bill presentment and/orpayment services. Preferably, the non-registered requesting user isregistered via communications 222 in step 340. It will of course benoted that although communications 222 are shown in FIG. 2 forcompleteness, since user A has pre-registered, these communication wouldnot actually occur with station 110A but would be required, for example,with station 110D in order to register user D.

As indicated in step 345, the central processor 140A retrieves theapplicable billing information from the database 140B2 of memory 140Bresponsive to the access request from station 110A, as indicated bycommunication 225. The retrieved information is then communicated by thestation 140, as directed by central processor 140A, to the user station110A via communication 230, as indicated in step 350. In step 355, thecentral processor 140A receives a payment instruction via communication235 from the user station 110A. Based upon the instruction, the centralprocessor 140A generates remittance information in step 360 and directsthe storage of the remittance information in the database 140B2 ofmemory 140B in association with the user H identifier via thecommunication 240, as indicated in step 365. Remittance information mayinclude such information as the name of the payer, the payer's address,phone number, and account number with the payee, among otherinformation. Generated and stored remittance information is particularlybeneficial in those situations in which the central station 140 storesbill information for an unregistered user who becomes registered andelectronically pays the bill represented by the stored bill information.The remittance information informs the biller that the bill has beenpaid and that the customer is now a registered user.

The central processor 140A also generates a pay directive in step 370.In step 375, the generated pay directive is transmitted. As discussedabove, payment may be accomplished in various ways. However, preferablythe directive is to the financial institute I, represented by station130A, which maintains an account for the user A. The directive istransmitted via communication 245 to the FI station 130A and the paymentfunds are transferred electronically in communication 270, for depositin the user H account maintained at financial institute K, representedby FI station 130C. Of course, the payment directive may not beelectronic, it may be a paper directive, such as a draft or check. And,the payment directive, whether electronic or paper, may direct thatfunds from the payer's account be transferred to, electronically orotherwise, an account associated with the central clearinghouse station140. The financial institute K may, if desired, notify user H viacommunication 275 to station 110H, of the receipt of the deposit, asindicated in step 377. It should be understood that the generation andstorage of the remittance information and the generation and/ortransmission of the pay directive may occur substantially simultaneouslyor at different times, as will be described further below.

Optionally, although not preferably, an email or other notice is sentvia communication 250 to the user station 110H, to notify the user ofthe availability of the stored remittance information, as indicated instep 380. In step 385, a request for remittance information istransmitted in communication 255 from the user station 110H and receivedby the central station 140. Communications 260, between centralclearinghouse processor 140A and memory 140B, result in the retrieval ofthe remittance information from the database 140B2 in response to therequest, as indicated in step 390. The retrieved information istransmitted from the central station 140, as directed by processor 140A,to the user station 110H via communication 265, as indicated in step395.

User A can also communicate with financial institute I, preferably viacentral station 140, to electronically confirm the transfer of thepayment amount from its account and the user H can also communicate withfinancial institute K, preferably via central station 140, toelectronically confirm the transfer of payment amount to its account, aswill be understood by those skilled in the art.

As introduced above, electronic billing information may be stored in thedatabase 140B2 of memory 140B even for those customers who are notregistered with the central station 140. Further, electronic billinginformation may be stored in the database 140B2 for registered userseven if the particular registered user has not requested electronic billpresentment. Accordingly, the central station 140 operates to directregistered users who contact the central station 140 to make payments onthe basis of paper bills to the electronic billing information availableon the database 140B2 of memory 140B, as will be discussed below.

FIG. 4 is similar to FIG. 2 except that communications 215 and 220 arereplaced by communications 400, 405, and 410, which will be describedbelow. As shown in FIGS. 4 and 5, a payment instruction, to pay a paperbill received in the mail by registered user C, is transmitted bycommunication 400 from the user station 110C to the central station 140,and received by the central station processor 140A, as indicated by step500. In communication 405, the central station 140, directed by thecentral processor 140A, notifies the applicable user station 110C, ofthe availability of electronic billing information which is stored inthe database 140B2 of memory 140B in association with the user Cidentifier, as reflected in step 505. The central station processor 140Agenerates an inquiry to the user C, inquiring if the user C wishes toreceive the billing information. The inquiry is also transmitted fromcentral station 140 to user station 110C in communication 405. The userC responds to the query in communication 410 from the payer 110C tocentral station 140, as indicated in step 510. If the user C responds inthe affirmative, i.e. indicating a desire to access to the billinginformation stored in the database 140B2, operations continue aspreviously described beginning with step 345 of FIG. 3. If the user Cresponds in the negative, operations continue as previously describedbeginning with step 360 of FIG. 3.

A registered user may pay any person or entity via the network 100.Thus, a user may direct that payment be made to a registered user,whether or not that user is also an electronic biller. Also, a user mayalso direct payment to an unregistered user who has no establishedrelationship with network 100. FIG. 6 depicts the communicationsnecessary to perform electronic bill payment of a paper bill received bya registered user via mail delivery from an unregistered user.Communications will be described in conjunction with FIG. 7. Incommunication 600, a payment instruction, to pay the paper bill receivedby mail by registered user B, is transmitted from user station 110B tocentral station 140. The instruction is received by the central stationprocessor 140A, as indicated in step 700. The central station processor140A, in step 705, makes a determination as to whether or not payee F isregistered. If payee F is determined to be a registered user, processingcontinues with step 360 of FIG. 3.

If payee F is determined to be unregistered, central station processor140A, in step 706, makes a determination as to whether or not payee F isincluded in database 140B2. If payee F is not included, in step 707, thecentral station processor generates and stores a user identifier forpayee F in database 140B2. Operations continue with step 710. If payee Fis included in database 140B2, operations proceed directly to step 710.

The central processor 140A generates remittance information in step 710.The generated remittance information is preferably identical to thatgenerated in step 360 of FIG. 3, but could be in a somewhat modifiedform particularly suitable for paper remittance if so desired.Optionally, the generated remittance information may be stored indatabase 140B2 at step 715 and via communication 601. In step 718 thecentral station processor 140A generates check/draft information. Thegenerated remittance and check/draft information is transmitted incommunication 605 to a printer 650 which, in step 720, prints a papercheck/draft and associated remittance information which form a paymentdocument 655. The payment document 655 is delivered to payee F.

Preferably, the central processor 140A also drives the printer 650 toprint additional information notifying payee F of the availability ofelectronic bill presentation and payment services through the centralstation 140. As payee F receives more and more payments via the centralstation 140, payee F will become more and more motivated to present itsbills and receive its payments electronically over the network 100, andhence to become a registered user of the network. If, as depicted atstep 715, the remittance information has been stored in database 140B2,the additional information could also include notifying the payee F ofthe availability of the stored remittance information and inviting payeeF to view the stored remittance information available at centralclearinghouse station 140 via the network 100.

FIG. 8 shows a somewhat simplified depiction of a relational database800 suitable for use as database 140B2. FIG. 8 will be helpful inunderstanding the robustness of the central station 140. As indicatedabove, preferably each user for whom billing or remittance informationis generated, whether or not a registered user, is identified with auser identifier. That is, all of the user identifiers are associatedwith users that have either registered, been paid through the centralstation 140 at the request of a registered user or have billinginformation which is stored at the central database 140B2 at the requestof a registered user.

As shown in FIG. 8, the user identifiers are stored in column 805 of therelational database 800. The registration status of each identified useris stored in column 810, in association with the applicable identifier.As shown, the users A-C, E, and H-L are registered users, while users D,F and G are unregistered users. It should be noted that each of thefinancial institutes I-L are shown to be registered and hence have theability to electronically present and pay bills, in addition to theirpreviously described functions. The applicable financial institutesidentifiers are also stored in column 815 for each of the registeredusers. Along with the financial institute identifiers are storedapplicable payment account numbers (PA) and/or debit account numbers(DA) in column 815. The credit account and the debit account may be thesame account. In column 820 billing information can be temporarilystored for each user. As shown, billing information is currently storedfor certain registered users as well as certain unregistered users. Incolumn 825 remittance information can be temporarily stored for eachuser. As shown, remittance information is currently stored for certainregistered users as well as certain unregistered users.

In an especially preferred feature of the invention, individualuser-class databases, in addition to database 140B2, are maintained bycentral processor 140A and stored in memory 140B. Database 140B3 is alist of registered users/billers, registered users who haveelectronically presented a bill. Database 140B4 is a list of registeredusers/customers, registered users who have had a bill electronicallyposted to central station 140 by a registered user/biller for payment.Database 140B5 is a database of unregistered users/customers,unregistered users who have had an bill electronically posted to centralstation 140 by a registered user/biller for payment. As should beunderstood, a registered user can appear in one of or both of databases140B3-140B4. Central processor 140A generates the information stored inthese databases each time billing information is transmitted to centralstation 140A by a registered user.

FIG. 9 shows a simplified exemplary depiction of database 140B3. Thisdatabase can include, in addition to information identifying theincluded registered users/billers 905, billing information about thebills each user has electronically presented through central station140, 910. FIG. 10 depicts the processing steps necessary to maintainthis database. Following step 325 of FIG. 3, in step 1010 centralprocessor 140A accesses database 140B3 to determine if the registereduser/biller is included in database 140B3. If the registered user/billerelectronically presenting the bill has previously electronicallypresented a bill, the user will already be included in the database. Ifyes, billing information for the current bill can is stored in database140B3 and associated with the registered user/biller identifier in steps1015. Operations then continue with step 328 of FIG. 3. If theregistered user/biller is not included in database 140B3, informationidentifying the user is added to the database in step 1020. Operationsthen continue with step 1015.

This database serves to dynamically maintain a list of users who areelectronic billers. As a user becomes an electronic biller, whether anew user or an existing user adopting electronic billing, that user isadded to this database. Thus, database 140B3 always contains an accurateand current list of users who are electronic billers. The operator ofcentral clearinghouse station 140 at all times knows which of the usersare electronic billers. Thus, this database may be used in notifying aregistered user that a payee to whom the user is directing payment is anelectronic biller, as discussed above. Also, this database may be usedin determining if the payee to whom the user is directing payment haselectronically presented a bill for this user.

FIG. 11 shows a simplified exemplary depiction of database 140B4. Thisdatabase can include, in addition to information identifying theincluded registered users/customers 1105, billing information about eachof the bills posted to central station 140 for the user, 1110. FIG. 12depicts the processing steps necessary to maintain this database.Following an affirmative decision in step 321, in step 1210, centralprocessor 140A accesses database 140B4 to determine if the registereduser/customer to whom the electronic bill is directed is included indatabase 140B4. If the registered user/customer has previously had anelectronic bill posted for payment by a registered user, theuser/customer will already be included in the database. If yes, billinginformation for the current electronic bill is stored in database 140B4and associated with the registered user/customer identifier in step1215. Operations then continue with step 325 of FIG. 3. If theregistered user/customer is not included in database 140B4, informationidentifying the user is added to the database in step 1220. Operationsthen continue with step 1215.

This database serves to dynamically maintain a list of all customers forwhom billing information is stored at central station 140. This databasemay be used in notifying a user that electronic billing information isstored at central station 140, as discussed above.

As should be understood, the operations depicted in FIGS. 10 and 12 maytake place simultaneously, or the operations depicted in FIG. 10 maytake place before those depicted in FIG. 12, or vice-versa.

FIG. 13 shows a simplified exemplary depiction of database 140B5. Thisdatabase can include, in addition to information identifying theincluded unregistered users/customers 1305, billing information abouteach of the bills posted to central station 140 for the unregisteredusers 1310 by a registered user. FIG. 14 depicts the processing stepsnecessary to maintain this database. Following a negative determinationin step 321 of FIG. 3, in step 1410 central processor 140A accessesdatabase 140B5 to determine if the unregistered user/customer to whomthe electronic bill is directed is included in database 140B5. If theunregistered user/customer has previously had an electronic bill postedfor payment by a registered user, the user/customer will already beincluded in the database. If yes, billing information for the currentelectronic bill is stored in database 140B5 and associated with theunregistered user/customer identifier in step 1415. Operations thencontinue with step 322 of FIG. 3. If the unregistered user/customer isnot included in database 140B5, information identifying the user isadded to the database in step 1420. Operations then continue with step1415.

A beneficial feature of the invention is that a registered user canstore at central clearinghouse station 140 a list of payees the user mayplan to pay electronically. Each user's individual list is stored in theform of yet another database in memory 140B, or some other storagedevice (not shown) connected to the central processor 140A. FIG. 15 is asimplified exemplary depiction of database 140B6 containing a list ofpayees for user B. This database is known as a payee pick-list. A payeepick-list may include payee identifiers 1501, street addresses 1502,cities 1503, states 1504, zip codes 1505, phone numbers 1506, and theusers' consumer account numbers 1507 with the payee, among otherinformation. The payee pick-list can include payees who are bothregistered users and unregistered users.

FIGS. 16 and 17 depict the communications and steps necessary tomaintain a payee pick-list for registered user B. FIG. 16, communication1601, depicts a communication over which user B transmits informationidentifying a payee for inclusion in a payee pick-list for user B. InFIG. 17, at step 1701, the transmitted information is received at thecentral station 140. Central processor 140A accesses database 140B2 anddetermines if a user identifier identifying the payee is stored indatabases 140B2 of memory 140B via communication 1610 at step 1707. Ifthe payee is in memory 140B, at step 1710, the payee's user identifieris stored in registered user B's payee pick-list via communication1620A. If a user identifier is not stored in memory 140B, at step 1715 auser identifier is generated for the payee. Then, at step 1710, the useridentifier is stored in payee pick-list database 140B6 via communication1620B. The payee pick-list may be established at registration, or anytime after registration. Also, at any time, a registered user may addto, delete from or update information in its payee pick-list.

A registered user may establish a communications session with centralstation 140 at any time. FIG. 18 depicts exemplary operations duringsuch a communications session. Central station transmits, at step 1801,user B's payee pick-list to user B via communication 1602. User B maythen select, at step 1810, a payee from its payee pick-list to whichpayment is to be directed. This selection, and associated paymentinstructions, are transmitted to central station 140 via communication1603 and received at step 1820. Thereafter, operations continue withstep 705 of FIG. 7.

It should be understood that multiple payees may be selected from thepayee pick-list. Also, it should be understood that user B may at alltimes pay a payee not included in his or her payee pick-list.

FIG. 19 shows a simplified exemplary depiction of a payee pick-listscreen transmitted to user B and displayed on computer display 1900. Ina particularly preferred aspect of the invention, the payee pick-listtransmitted to a registered user will include other information beyondthat identifying the included payees 1915A-D. The payee pick-list caninclude a hyper-link selectable to cause central processor 140A totransmit to user B a pay directive screen to be displayed on computerdisplay 1900 which includes all necessary information to make a payment,as shown in exemplary FIG. 20. This screen includes the payee name 2001,billing address information 2010, and a payment amount to be completedby the user 2015.

Preferably, the payee pick-list transmitted to user B includes anindication that an electronic bill from a payee, or payees, is stored indatabase 140B2 for user B, as discussed above and depicted here at 1905Aand 1905B. Payer B, also as discussed above, may select to view thestored electronic bill or bills. The indication that an electronic billis stored at the central clearinghouse station 140 can be a hyper-linkselectable by user B to cause central processor 140A to transmit thestored billing information to user station 110B.

The payee pick-list presented to user B also can include an indicationthat a payee included in user B's payee pick-list offers electronic billpresentment, whether or not billing information from that particularpayee for user B is currently stored in memory 140B, 1910A and 1910B.The indication that an included payee offers electronic bill presentmentmay be a hyper-link selectable by user B to cause central processor 140Ato inform the selected payee that user B has selected electronic billpresentment for future bills. Central clearinghouse station 140 mayinform the payee of the selection by a network communication or bytraditional mail or telephonic communication. Or, selection of thehyper-link may cause central processor 140A to transmit to user B ascreen for display which includes electronic billing options, as shownin simplified exemplary FIG. 21. As shown, the options can includereceiving both an electronic bill and a paper copy of the bill 2101, orreceiving electronic bills only 2105. Also, a user can select to receiveelectronic bills and paper bills for a period of time, and thereafterreceive only electronic bills, perhaps for one billing cycle or forthree months 2108A and 2108B. It should be understood that the periodcan be any period. The user can also sign-up for a trial subscription ofelectronic billing 2110. That is, a user will receive a limited numberof electronic bills along with paper bills, then billing will revertback to exclusively paper billing. Yet another option is to receive ane-mail notification of any future stored billing information beingavailable at central clearinghouse station 140, 2115. It should beunderstood by one skilled in the art that other options are possible,though not depicted in FIG. 21.

FIGS. 22 and 23 present operations of central processor 140A incompiling the information to be presented to a user along with thepayees included in the user's payee pick-list. After user B hasestablished a communication with central clearinghouse station 140, atstep 2201, central processor 140A accesses user B's stored payeepick-list database 140B6 and the registered user/biller database. 140B3.At step 2210, central processor 140A determines the common entriesbetween the two databases. For any common entry, central processor 140Astores an indication in the user B payee pick-list database associatedwith the user identifier for the common entry that the payee is anelectronic biller, as depicted at step 2220.

At step 2301, central processor 140A accesses user B's stored payeepick-list database 140B6 and database 140B5. As shown in step 2310,central processor 140A determines if any of the user B payee pick-listpayees also have stored billing information for user B at the centralclearinghouse station 140. For any payees having stored billinginformation for user B at the central station, central processor 140Astores an indication in the user B payee pick-list database associatedwith the user identifier for the payee having stored the bill at thecentral clearinghouse station 140 at step 2315.

It should be understood that database 140B2 may be accessed in place ofeither of or both of databases 140B3 and 140B4, as depicted in steps2201 and 2301. However, processing is most efficient when accessingdatabases 140B3 and/or 140B4, as database 140B2 contains a greatervolume of information than either of these databases.

It should also be understood that the steps in FIGS. 22 and 23 may takeplace simultaneously, or the steps of FIG. 22 may follow the steps ofFIG. 23, or vice versa. In any event, the steps discussed and shownfurther reveal the robustness of central processing station 140. Thecentral processor 140A functions to dynamically indicate availability ofelectronic bill presentment and availability of stored billinginformation. Prior to each transmission of a user's payee pick-list, thecentral processor 140A determines which of the payees are electronicbillers and which of those have submitted billing information to thecentral processor 140A. Since, as described above, each electronicbiller is included in the user/biller database, and since that databaseis updated every time an electronic bill is submitted, each time centralprocessor 140A determines the common entries between the user/billerdatabase and a user payee pick-list database, the results of thatdetermination are accurate and up-to-date.

FIG. 24 depicts an alternative implementation of the present invention.Due to the billing information stored associated with the useridentifier for each registered user/biller in database 140B3, the stepsof FIGS. 22 and 23 can be combined. At step 2401, central processor 140Aaccesses both the payee pick-list database for user B 140B6 and theregistered user/biller database 140B3. The central processor 140Adetermines any common user identifiers between the two databases at step2410. With the billing information being stored in database 140B3,central processor 140A next determines if any of the billing informationstored in association with a common entry is for a bill directed to userB, as depicted at step 2420. An indication that a payee is an electronicbiller and an indication of any stored billing formation is added touser B's payee pick-list associated with the user identifier of theelectronically presenting user at step 2425 for any common entries andany of the common entries with stored billing information directed touser B.

In yet another implementation, the processing necessary to includefurther information beyond payee identifiers presented with a user'spayee pick-list can occur in a different manner from that describedabove. FIGS. 25 and 26 depict alternative communications and operationsin storing a payee in user B's payee pick-list database. As discussedabove, prior to any transmission of user B's pick-list to user B, adetermination is made by central processor 140A as to the electronicbilling status of each included payee. This electronic billing statusincludes determining if the payee is an electronic biller and if thepayee has billing information for the user stored in memory 140B.Alternatively, this determination can be made whenever user B adds apayee to its payee pick-list, whenever a new electronic biller is addedto the registered user/biller database 140B3, and whenever a new payeeis added to the registered user/customer database 140B4.

Following steps 1701 of FIG. 17, the processing to add a payee to thepayee pick-list is somewhat different than described above. As shown inFIG. 26, if central processor 140A determines that the payee is notincluded in memory 140B at step 2606, processing continues as describedabove. However, if central processor 140A determines that the payee isincluded in memory 140B, operations continue with step 2607. Centralprocessor 140A stores the payee's user identifier in user B's payeepick-list. At step 2610, central processor 140A accesses database 140B3via communication 2505 of FIG. 25 to determine if the payee is aregistered user/biller. If not, operations end. If the payee is aregistered user/biller, an indication is added to database 140B6 viacommunication 2510 that the payee is a registered user/biller at step2615.

Operations continue with step 2620. Via communication 2515, centralprocessor 140A accesses database 140B4 to determine if the payee hasstored billing information for user B in this database. If not,operations end. If so, an indication is added to database 140B6 viacommunication 2520 and at step 2625 that billing information is storedfor user B. As a result of the processing depicted in steps 2610-2625,whenever a user adds a payee to its payee pick-list, an accurate andcurrent indication of electronic billing status is included in the payeepick-list for that payee.

It should be understood that the processing depicted in steps 2610-2625is similar to that depicted in steps 2201-2220 and 2301-2320. Thus, thealternative use of database 140B2 discussed above in relation to thesesteps also applies to the processing depicted in steps 2610-2625.

When the indication of electronic billing status is created at initialstorage of a payee identifier in an individual payee pick-list insteadof prior to each transmission of the list to the user, each individualpayee pick-list is kept up current the following processing. Thisprocessing is necessary, as a user/payee may become an electronic billersubsequent to that user/payee being added to an individual payeepick-list. Also, an electronic biller may post billing information tothe central station 140 for an individual user subsequent to that useradding that user/payee to its individual payee pick-list.

Central processor 140A serves to maintain yet another database, known asa master payee pick-list. This database is also stored in memory 140B asdatabase 140B7. The master payee pick-list is a list of every payeewhich appears on at least one individual payee pick-list. FIG. 27 is asimplified exemplary depiction of the database. In addition to useridentifiers for each payee appearing in an individual payee pick-list2701, the database also contains an indication of each user on whoseindividual payee pick-list the payee appears 2710, and the payee streetaddress 2711, city 2712, state 2713, zip code 2714, and phone number2715. The master payee pick-list is kept current by the followingprocessing depicted in FIGS. 28 and 29.

Whenever a registered user adds a payee to its individual payeepick-list, following step 1706 of FIG. 17, at step 2801 of FIG. 28 andvia communication 2525, central processor 140A determines if the payeeis included in the master payee pick-list. If not, the user identifierfor the payee, along with the other information described above, isstored in the master payee pick-list at step 2805 and via communication2530. Operations continue with step 2810. If the payee is included inthe master payee pick-list, at step 2810, the user identifieridentifying the individual user adding the payee to its individual payeepick-list is stored in the master payee pick-list associated with thepayee identifier, via communication 2535.

Whenever central processor 140A adds a new registered user/biller todatabase 140B3, central processor 140A also determines if the addedregistered user/biller is included in database 140B7, as depicted inFIG. 29, step 2901 and via communication 2540. Step 2901 follows step1015 of FIG. 10. If the new registered user/biller is not included inthe master payee pick-list database 140B7, operations continue with step328 of FIG. 3. If the new registered user/biller appears in the masterpayee pick-list, operations continue with step 2910. The centralprocessor 140A adds an indication to each individual payee pick-listdatabase in which the new registered user/biller appears as a payee thatthe new registered user/biller is an electronic bill presenter viacommunication 2545. Due to the processing depicted in steps 2901 and2910, each individual payee pick-list is kept current as to which of theincluded payees are electronic bill presenters.

Whenever central processor 140A adds a new registered user/customer todatabase 140B4, central processor 140A also determines if the newregistered user/customer maintains a payee pick-list at centralclearinghouse station 140. As depicted in FIG. 30 following step 1215 ofFIG. 12, at step 3001 and via communication 2550, central processor 140Adetermines if the new registered user/customer maintains a payeepick-list. If the new registered user/customer does not have a payeepick-list, operations continue with step 325 of FIG. 3. On the otherhand, if the new registered user/customer does have a payee pick-list,central processor 140A determines if the biller presenting theelectronic bill is included in the individual payee pick-list at step3005 and via communication 2650. If not, operations continue with step325 of FIG. 3. If the biller is included in the individual payeepick-list, an indication is added to the individual payee pick-list thatthere is stored electronic billing information available, as depicted instep 3010 and communication 2655. Operations continue with step 325 ofFIG. 3. Because central processor 140A determines, for each new entryinto the registered user/customer database, if a customer maintains apayee pick-list and if that pick-list contains information identifyingthe payee electronically presenting the bill, central processor 140A isable to keep the electronic billing status information in eachindividual payee pick-list current.

Central processor 140A can determine if each new entry into theregistered user/customer database 140B4 maintains a payee pick-list andif the biller is included in the individual payee pick-list by accessingthe master payee-pick list, as depicted in FIG. 31. The followingprocessing replaces the processing depicted at steps 3001 and 3005 ofFIG. 30. Central processor 140A accesses the master payee pick-list, asdepicted in step 3101. The central processor 140A next determines if thenew user/customer is included in the master payee pick-list, at step3105. If not, operations continue with step 325 of FIG. 3. If the newuser/customer is included in the master payee pick-list, centralprocessor 140A determines if the customer is associated with the billerin the master payee-pick list, step 3110. If not, operations continuewith step 325 of FIG. 3. If yes, operations continue with step 3010 ofFIG. 30.

Because central processor 140A maintains user-class databases for notonly registered users, but also for unregistered users, centralprocessor 140A can notify a newly registered user of any existing storedbilling information for the newly registered user.

FIG. 32 depicts the steps necessary to inform a newly registered user ofthe existence of stored billing information. At step 3201 centralprocessor 140A receives registration information. This information,along with a user identifier, is stored in database 140B2, as depictedin step 3202. Central station 140A accesses the unregistereduser/customer database 140B5, as depicted in step 3205, and determinesif the newly registered user is included in the database. If the newregistered user is included in the database, the newly registered useris optionally notified of the stored billing information at step 3210.After optional notification, and at step 3215, the stored billinginformation is removed from the unregistered user/customer database140B5 and stored in the registered user/customer database 140B4, keepingboth the unregistered and registered user/customer databases current.

It will also be recognized by those skilled in the art that, while theinvention has been described above in terms of one or more preferredembodiments, it is not limited thereto. Various features and aspects ofthe above described invention may be used individually or jointly.Further, although the invention has been described in the context of itsimplementation in a particular environment and for particular purposes,e.g. electronic bill presentment and/or payment, those skilled in theart will recognize that its usefulness is not limited thereto and thatthe present invention can be beneficially utilized in any number ofenvironments and implementations. Accordingly, the claims set forthbelow should be construed in view of the full breath and spirit of theinvention as disclosed herein.

1. A method for notifying a person of the availability of billinginformation, comprising: storing, in a first data store, billinginformation associated with bills of a biller for its customers;storing, in a second data store, identity information identifyingunregistered persons having billing information stored in the first datastore; receiving, via a wide area network from a person who is currentlyunregistered, registration information identifying the person; comparingthe received registration information with the identity informationstored in the second data store; determining, based on the comparison,if the received registration information identifies a customer of thebiller; and transmitting, to the person via the wide area network, anotice of the availability of the stored billing information, if thereceived registration information is determined to identify the customerof the biller; wherein the comparing and determining are performed by acomputer.
 2. The method of claim 1, further comprising: receiving, fromthe person via the wide area network responsive to the transmittednotice, a request for the stored billing information; and transmitting,to the person via the wide area network responsive to the receivedrequest, the stored billing information associated with the bill of thebiller for the person.
 3. The method of claim 1, wherein the biller is afirst biller, and further comprising: also storing, in the first datastore, billing information associated with bills of a second biller forits customers; determining, based on the comparison, if the receivedregistration information identifies a customer of the second biller; andtransmitting, to the person via the wide area network, a notice of theavailability of the stored billing information of the second biller, ifthe received registration information is determined to identify thecustomer of the second biller.
 4. The method of claim 3, wherein: it isdetermined that the received registration information identifies thecustomer of the first biller and the customer of the second biller; andthe notices of the availability of the stored billing information of thefirst and the second billers are transmitted in a single consolidatedmessage.
 5. The method of claim 1, wherein the biller is a first biller,and further comprising: also storing, in the first data store, otherbilling information associated with bills of a second biller for itscustomers; receiving, via a wide area network from another person who iscurrently unregistered, other registration information identifying theother person; comparing the received other registration information withthe identity information stored in the second data store; determining,based on the comparison, if the other received registration informationidentifies a customer of the second biller; and transmitting, to theother person via the wide area network, a notice of the availability ofthe stored other billing information, if the received other registrationinformation is determined to identify the customer of the second biller;6. A system for notifying a person of the availability of billinginformation, comprising: a first data store having billing informationassociated with bills of a biller for its customers; a second data storehaving identity information identifying unregistered persons havingbilling information stored in the first data store; and a processorhaving the logic (i) to receive registration information identifying aperson who is currently unregistered, (ii) to determine if the personidentified in the received registration information is a customer of thebiller based on the stored identity information, and (iii) to directthat the person be notified of the availability of the stored billinginformation, if the person is determined to be the customer of thebiller.
 7. The system of claim 6, wherein: the processor also has thelogic (i) to receive a request from the person for the stored billinginformation responsive to the directed notification, and (ii) to direct,responsive to the received request, delivery of the stored billinginformation associated with the bill of the biller for the person. 8.The system, of claim 6, wherein: the processor (i) receives theregistration information via a wide area communications network, and(ii) directs that the person be notified by transmission of the noticeof availability of the stored billing information to the person via thewide area communications network.
 9. The system of claim 6, wherein: thebiller is a first biller; the first data store also has billinginformation associated with bills of a second biller for its customers;the processor has the logic to also determine, based on the storedidentity information, if the person identified in the receivedregistration information is a customer of the second biller, and todirect that the person be notified of the availability of the storedbilling information associated with the bills of the second biller, ifthe person is determined to be the customer of the second biller. 10.The system of claim 9, wherein: if the person is determined to be thecustomer of both the first and the second billers, the processor directsthat the person be notified of the availability of the stored billinginformation associated with the bills of the first and the secondbillers by a single consolidated notice.
 11. The system of claim 6,wherein: the biller is a first biller; the first data store also hasother billing information associated with bills of a second biller forits customers; the processor also has the logic (i) to receive otherregistration information identifying another person who is currentlyunregistered, (ii) to determine if the other person identified in thereceived other registration information is a customer of the secondbiller based on the stored identity information, and (iii) to directthat the other person be notified of the availability of the storedother billing information, if the other person is determined to be thecustomer of the second biller.
 12. A networked system, includingmultiple network stations interconnected by a wide area communicationsnetwork, for notifying a person of the availability of billinginformation, comprising: a first data store including billinginformation associated with bills of a biller for its customers; asecond data store including identity information identifyingunregistered persons having billing information stored in the first datastore; a first network station representing a bill payment serviceprovider; and a second network station representing a person currentlyunregistered with the bill payment service provider, for transmittingregistration information identifying the person; wherein the firstnetwork station (i) receives the transmitted registration information,(ii) determines, based the stored identity information, if the personidentified in the received registration information is a customer of thebiller, and (iii) if the person identified in the received registrationinformation is determined to be the customer of the biller, transmits anotice of the availability of the stored billing information to thesecond network station.
 13. The networked system of claim 12, wherein:the first data store and the second data store are located at the firstnetwork station.
 14. The networked system of claim 12, wherein: thesecond network station receives the transmitted notice of availabilityand transmits a request for the available billing information to thefirst network station, responsive to the received notice.
 15. Thenetworked system of claim 14, wherein: the first network stationreceives the transmitted request for the available billing informationand, responsive to the received request, (i) retrieves the billinginformation associated with the bill of the biller for the person fromthe first data store and (ii) transmits the retrieved billinginformation to the second network station; and the second networkstation receives the transmitted billing information and presents thereceived billing information to the person.
 16. The networked system ofclaim 12, wherein: the biller is a first biller; the first data storealso stores billing information associated with bills of a second billerfor its customers; the notice of the availability of the stored billinginformation is a notice of the availability of the stored billinginformation associated with bills of the first biller; and the firstnetwork station (i) also determines, based the stored identityinformation, if the person identified in the received registrationinformation is a customer of the second biller and (ii), if the personidentified in the received registration information is determined to bethe customer of the second biller, transmits a notice of theavailability of the stored billing information associated with bills ofthe second biller to the second network station.
 17. The networkedsystem of claim 16, wherein: the first network station determines thatthe person identified in the received registration information is thecustomer of both the first and the second billers and transmits a singlemessage having the notices of the availability of the stored billinginformation associated with bills of both the first and the secondbillers to the second network station.
 18. The networked system of claim17, wherein: the second network station receives the transmitted messageand transmits a request for the available billing information,responsive to the received message; and the first network stationreceives the transmitted request and, responsive to the receivedrequest, (i) retrieves the stored billing information associated withthe bills of the first biller and the second biller for the person fromthe first data store and (ii) transmits the retrieved billinginformation to the second network station.
 19. The networked system ofclaim 12, further comprising: a third network station representinganother person currently unregistered with the bill payment serviceprovider, for transmitting other registration information identifyingthe other person; wherein the biller is a first biller; wherein thefirst data store also stores other billing information associated withbills of a second biller for its customers; wherein the first networkstation also (i) receives the transmitted other registrationinformation, (ii) determines, based the stored identity information, ifthe other person identified in the received other registrationinformation is a customer of the second biller, and (iii) if the otherperson identified in the received other registration information isdetermined to be the customer of the second biller, transmits anothernotice of the availability of the stored billing information to thethird network station.
 20. The networked system of claim 19, wherein:the person identified in the received registration information isdetermined to be the customer of the first biller and the other personidentified in the received other registration information is determinedto be the customer of the second biller; the notice of the availabilityof the stored billing information transmitted to the second networkstation is a notice of the availability of the stored billinginformation associated with bills of the first biller; and the othernotice of the availability of the stored billing information transmittedto the third network station is a notice of the availability of thestored billing information associated with bills of the second biller.